Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update list system settings schema #50

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

zhao-gang
Copy link
Contributor

@zhao-gang zhao-gang commented Jun 6, 2024

This pull request depends on #49

Do not depend on other PR so it's better to review this.

@zhao-gang
Copy link
Contributor Author

zhao-gang commented Jun 6, 2024

list_system_settings_schema seems not consist for settings with boolean value.

For other settings, list_system_settings_schema will return all valid values for that settings. For boolean settings, it will return true or false, and currently the value is used to check if this setting is supported. It's not like other settings that checking if the value is empty.

If changed boolean to array, these settings could also return all supported values (normally true and false) like the other settings. And it can also return empty list as not supported just as the other settings do.

This PR includes commit from my previous PR as I think it would be easy to merge this if my previous PR is merged. I can separate them if needed.

System settings support enable / disable should also return all valid values like other settings. Change boolean to array and the array contains boolean value (true for enable and false for disable).

Can set array to empty if the settings don't support to be set.
@zhao-gang zhao-gang force-pushed the update-list-system-settings-schema branch from 285a7c7 to 97c87cd Compare June 7, 2024 01:22
@bgy36ww
Copy link
Contributor

bgy36ww commented Jun 24, 2024

Hi Zhao,

There is an issue with doing this. I understand this is a good way to reflect what's supported and what's not. But it does not reflect the spec correctly. We will need to change the spec first before changing the compliance suite. Can you make a PR there first?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants